Credit card payments

Use this data to verify the credit card payment flow.

You can use these test cases to test your integration for credit card payments. When you create a payment request with either the amount, or card number - a certain result is triggered.

API method Scenario Type Trigger amount Trigger card number

The reservation fails at the 3D Secure verification attempt.

 3DSecureFail 4.66
  • Pattern: ????????????0466
  • Visa: 4140000000000466
  • MasterCard:  5550000000000466

The reservation returns a technical error at the 3D Secure verification attempt.

3DSecureError 4.67
  • Pattern: ????????????0467
  • Visa: 4180000000000467
  • MasterCard: 5500000000000467

The reservation succeeds after a successful 3D Secure verification.

 3DSecureWork 4.68
  • Pattern ????????????0468
  • Visa 4130000000000468
  • MasterCard 5590000000000468

If the M character in the credit card number is 1, the 3DSecure v2 method flow will be triggered.
If you use amount 44.44, the reservation will be exempted from 3DSecure, and will be soft declined. Then it will continue with one of the following flows depends on the credit card number you inserted.
If you use any other amounts, one of the following flows depends on the credit card number you inserted will be triggered.

API method Scenario Transaction status Trigger card number

The reservation was initiated and a frictionless flow was triggered.

 TransactionStatus.ACCEPTED
  • Visa: 411100000000051M or 457100000000081M
  • MasterCard: 517000000000001M
  • Example:  4111000000000511

The reservation was initiated and a challenge flow was triggered.

 TransactionStatus.CHALLENGE
  • Visa 411100000000112M or 457100000000062M
  • MasterCard 517000000000992M
  • Example:  4111000000001121

The reservation was initiated and a decoupled challenge flow was triggered.

 TransactionStatus.DECOUPLED
  • Visa: 411100000000013M or 457100000000123M
  • MasterCard:  517000000000553M
  • Example:  4111000000000131

In order to trigger the Authenticated or Rejected result upon authentication, please do so by clicking one of the following buttons in the Mock ACS (testbank):

API method Scenario Type Trigger amount Trigger card number

The payment fails because it is declined by the bank.

 Failed 5.66
  • Pattern: ????????????0566
  • Visa: 4180000000000566
  • MasterCard: 5500000000000566

The payment fails because of a technical error.

Error 5.67
  • Pattern: ????????????0567
  • Visa: 4130000000000567
  • MasterCard: 5590000000000567

The reservation succeeds after a successful 3D Secure verification.

 3DSecureWork 5.68
  • Pattern: ????????????0568
  • Visa: 4170000000000568
  • MasterCard: 5540000000000568

The CVV code is correct.

CVV Check Matched 5.71
  • Pattern: ????????????0571
  • Visa: 4100000000000571
  • MasterCard: 5560000000000571

The CVV code is not correct.

CVV Check MisMatched 5.72
  • Pattern: ????????????0572
  • Visa: 4190000000000572
  • MasterCard: 5510000000000572

The CVV code is not applicable.

CVV Check Not_Applicable 5.73
  • Pattern: ????????????0573
  • Visa: 4140000000000573
  • MasterCard: 5550000000000573

The card verification fails because the card is declined.

Failed 16.66
  • Pattern: ????????????1666
  • Visa: 4120000000001666
  • MasterCard: 5580000000001666

The card verification fails because of a technical error.

Error 16.67
  • Pattern: ????????????1667
  • Visa: 4160000000001667
  • MasterCard: 5530000000001667

Use this test case data to test fraud check responses.

API method Scenario Error type Amount Card Number
Fraud check Accept Accept 101
  • Visa: 4170000000000006
  • MasterCard: 5060000000000006
Fraud check Challenge. Challenge 102
  • Visa: 4170000000000121
  • MasterCard: 5250000000000121
Fraud check Deny. Deny

110
  • Visa: 4170000000000105
  • MasterCard: 5060000000000105
Fraud check Unknown. Unknown Not possible
  • Visa: 4170000000000113
  • MasterCard: 5110000000000113

Use this test case data to test the Transaction Risk Analysis / Low Risk Exemptions feature.

Test Cases Using Enforced Mode

You need to use the following request parameters in order to trigger any of the below test cases.

  • authentication[exemption]=TRA
  • authentication[exemption_mode]=Enforced

API method Scenario Amount Result Card Number
A payment with Low Risk exemption is successfully authorized. Any Success
  • Pattern: ????????????????
  • Visa: 4120000000000000
  • MasterCard: 5580000000000000
SCA is triggered. A soft decline is received when trying to exempt the payment with Low Risk exemption. 61.00 Soft decline Any test credit card that triggers the 3DSecure v2 method flow. You can find those test credit cards here.
  • Examples:  4111000000000511 or 4111000000001121
A hard decline is received when trying to exempt the payment with Low Risk exemption. 62.00 Hard decline Any test credit card that triggers the 3DSecure v2 method flow. You can find those test credit cards here.
  • Examples:  4111000000000511 or 4111000000001121

Use this test case data to test the back-office methods. For more information, see API methods for Merchant and Processor APIs.

Scenario Error type Amount Card Number
Fails at captureReservation Failed 7.66
  • Pattern: ????????????0766
  • Visa: 4170000000000766
  • MasterCard: 5540000000000766
Fails at captureReservation Error 7.67
  • Pattern: ????????????0767
  • Visa: 4120000000000767
  • MasterCard: 5580000000000767
Triggered at captureReservation 20 second delay 19.66
  • Pattern: ????????????1966
  • Visa: 4150000000001966
  • MasterCard: 5520000000001966

Triggered at captureReservation

( To create the chargeback object, capture the reservation, then go to the Merchant Information Interface, and under Home > Terminal Settings, click on Create test reconciliation data)

 Chargeback 19.67
  • Pattern: ????????????1967
  • Visa: 4150000000001967
  • MasterCard: 5520000000001967
Scenario Error type Amount Card Number
Fails at releaseReservation. Failed 8.66
  • Pattern: ????????????0866
  • Visa: 4120000000000866
  • MasterCard: 5580000000000866
Fails at releaseReservation. Error 8.67
  • Pattern: ????????????0867
  • Visa: 4160000000000867
  • MasterCard: 5530000000000867
Scenario Error type Amount Card Number
Fails at refundCapturedReservation Failed 9.66
  • Pattern: ????????????0966
  • Visa: 4160000000000966
  • MasterCard: 5530000000000966
Fails at refundCapturedReservation Error 9.67
  • Pattern: ????????????0967
  • Visa: 4110000000000967
  • MasterCard: 5570000000000967
Scenario Error type Amount Card Number
Fails at credit or createPaymentRequest with the appropriate type set. Failed 9.66
  • Pattern: ????????????0966
  • Visa: 4160000000000966
  • MasterCard: 5530000000000966
Fails at credit or createPaymentRequest with the appropriate type set. Error 9.67
  • Pattern: ????????????0967
  • Visa: 4110000000000967
  • MasterCard: 5570000000000967

Use this test case data to test the back-office methods for subscriptions. For more information, see API methods for Merchant and Processor APIs.

Scenario Error type Amount Card Number
Fails at chargeSubscription Failed 13.66
  • Pattern: ????????????1366
  • Visa: 4180000000001366
  • MasterCard: 5500000000001366
Fails at chargeSubscription Error 13.67
  • Pattern: ????????????1367
  • Visa: 4130000000001367
  • MasterCard: 5590000000001367
Fails at reserveSubscriptionCharge Failed 13.66
  • Pattern: ????????????1366
  • Visa: 4180000000001366
  • MasterCard: 5500000000001366
Fails at reserveSubscriptionCharge Error 13.67
  • Pattern: ????????????1367
  • Visa: 4130000000001367
  • MasterCard: 5590000000001367